Scenarios

Unix - Unix
When developing on a host Unix machine and compiling and debugging on a remote Unix machine, please note:

- The

rlogin tool, provided with the Unix operating system, is used.
- The debugger script remote_debug.sh, is located in
$SNIFF_DIR/bin directory. When you start the debugger remotely, this script is copied to the working environment root directory and is later used to start the debugger. You can set other debugger commands/parameters in the original script.

To access your working environments from both the host and the target machine, you can either mount directories or you can create symbolic links to access the working environment root directory so that it looks the same from both machines.
Windows - Unix
When developing on a host Windows machine and compiling and debugging on a remote Unix machine, please note:

- The

rlogin tool is delivered with SNiFF_EVAL and SNiFF_CROSS and has been adapted for remote compiling and debugging. Thus remote compile and debug is only supported by SNiFF+ if the supplied rlogin is used on Windows.
- The debugger script remote_debug.sh, is located in
%SNIFF_DIR%\bin directory. When you start the debugger remotely, this script is copied to the working environment root directory and is later used to start the debugger. You can set other debugger commands/parameters in the original script.

We require that all working environments are located on the Unix machine and are accessible on Windows. For details, please refer to Cross-platform setup -- Windows side. By doing so, nightly updates, administrative work like updating, and using SNiFF+'s Make Support on the target machine are much faster.